Skip to content

Updated assets/data.json to reflect #1727 fixes for development purposes & fix for #1460#1730

Merged
Simek merged 7 commits intoreact-native-community:mainfrom
JairajJangle:fix/1640-download-count
Jun 24, 2025
Merged

Updated assets/data.json to reflect #1727 fixes for development purposes & fix for #1460#1730
Simek merged 7 commits intoreact-native-community:mainfrom
JairajJangle:fix/1640-download-count

Conversation

@JairajJangle
Copy link
Copy Markdown
Contributor

@JairajJangle JairajJangle commented Jun 22, 2025

📝 Why & how

  1. Updated assets/data.json file to reflect fix: preserve npm download data for scoped packages (fixes #1640) #1727 fixes for development purposes.
  2. Fixed yarn data:update unusable on dev mode #1460 by adding an option in build-and-score-data.ts script to bypass Vercel store blob fetch and update and use assets/data.json instead; useful for development/debugging purposes.
  3. Updated Readme to explain the usage of ONLY_WRITE_LOCAL_DATA_FILE in build-and-score-data.ts.

✅ Checklist

  • Documented in this PR how to use the feature or replicate the bug.
  • Documented in this PR how you fixed or created the feature.

…munity#1640)

Scoped packages (starting with @) were losing their download counts
because individual npm data was being overwritten during bulk merge.
Now preserves existing npm data while still filling regular packages.
…eact-native-community#1460

use data.json from assets folder instead when ONLY_WRITE_LOCAL_DATA_FILE is set to true - useful in development mode
@JairajJangle JairajJangle changed the title Updated assets/data.json to reflect #1727 fixes for development purposes Updated assets/data.json to reflect #1727 fixes for development purposes & fix for #1460 Jun 22, 2025
@Simek
Copy link
Copy Markdown
Member

Simek commented Jun 24, 2025

Hey @JairajJangle, thanks for working on the Vercel Blob issue! 👍

When it comes to the updating data JSON, usually this is done by maintainers, and only when we change the structure of entries, so the local dataset reflects the changes. What would be added by regeneration now is just missing download counts and several new entries, which should not hinder the development process.

The reason for this approach is that reviewing diff on that file is quite hard, and updating that file often clobbers the git history a bit. So let's revert the data changes for now, I will follow up that soon, with some scheduled changes, the rest looks good! 👌

@JairajJangle
Copy link
Copy Markdown
Contributor Author

JairajJangle commented Jun 24, 2025

Hi @Simek! Sure, no problem! If that’s the case, totally understandable. I’ll go ahead and revert the assets/data.json changes and update the PR accordingly 👍

Thanks for the clarification! 🙌

EDIT: I have reverted the changes in assets/data.json and have updated the PR

Copy link
Copy Markdown
Member

@Simek Simek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for working on the issue, and all other updates in the process, great job! 💪

@Simek Simek merged commit 44009e9 into react-native-community:main Jun 24, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

yarn data:update unusable on dev mode

2 participants